TPUG - Toronto PET Users Group/TPUG Users Group CD/TPUG Users Group CD.iso/CRS/crs52.d81/unix311b.sfx/intro.1

Text File | 1990-02-12 | 19KB | 463 lines

╒NIX 128 V3.10 ═ANUAL           15 ╩ANUARY 1992                          ╨AGE 1


                              ╘ABLE OF ├ONTENTS:

           1.   ─ISTRIBUTION AND ╥IGHTS...........................1
           2.   ╥EVISIONS ╙INCE ╓ERSION 3.00......................1
           3.   ╔NTRODUCTION......................................2
           4.   ┬UILDING THE ╒NIX 128 ╙YSTEM......................2
           5.   ╠OGGING ╔N ╞OR ╘HE ╞IRST ╘IME.....................3
           6.   ├USTOMIZATION OF THE ╙HELL........................3
           7.   ╘HE ╙HELL.........................................4
           8.   ╞ILES AND ─IRECTORIES.............................5
           9.   ╟ETTING ╚ELP......................................5
           10.  ╨RINTING..........................................5
           11.  FTP...............................................6
           12.  NROFF.............................................8
           13.  AS................................................8
           14.  ┬┴╙╔├.............................................10
           15.  EMACS.............................................10
           16.  TIP...............................................11
           17.  DC................................................12
           18.  MAIL..............................................13
           19.  SPREAD............................................13
           20.  ═ISCELLANEOUS (GAMES, TAR, UUENCODE, STYLE).......14

1.  ─ISTRIBUTION AND ╥IGHTS:

╘HIS SYSTEM IS DISTRIBUTED WITHOUT WARRANTY OR GUARANTEE OF ANY KIND.   ╔T  MAY
BE  FREELY  DISTRIBUTED AS LONG AS IT'S INTACT WITH ALL DOCUMENTATION AND CODE.
╧F COURSE, ╔'D LIKE MY NAME TO STAY WITH THE PACKAGE, AND ╔ RETAIN  ALL  RIGHTS
TO  THE  SOURCE CODE THAT ╔ WROTE.  ┬UG REPORTS, GRIPES, A PALTRY $10 SHAREWARE
FEE IF YOU LIKE THIS PROGRAM MAY BE SENT TO:
             ╟REGG ╥IEDEL
             20 ┼LLBERT ╙TREET
             ╙MITHTOWN, ╬┘ 11787
(IT'S MY HOME ADDRESS, BUT IT'S A LITTLE MORE STABLE THAN MY COLLEGE  ADDRESS.)
╔ WILL PROBABLY GRADUATE ╙╒╬┘-┬INGHAMTON AROUND ╙PRING '93 - ╔ SHOULD RETAIN MY
├ONSULTANT ACCOUNT UNTIL THEN:  CONSP24 @ BINGVAXU.CC.BINGHAMTON.EDU

╘RADEMARKS:  ╒NIX IS A TRADEMARK OF ┴╘&╘.  ╙UN AND ╙UN╧╙ ARE TRADEMARKS OF  ╙UN
═ICROSYSTEMS.  ╘HE MAIN FONT USED IS TAKEN FROM ─ES╘ERM 2.00'S DES.AMIGASET.


2.  ╔NTRODUCTION:

╒NIX 128 V3.10 IS A ╒NIX BASED OPERATING SYSTEM  FOR  THE  ├OMMODORE  128.   ╔T
TAKES THE BEST POINTS FROM ┴╘&╘ ╙YSTEM ╓, ╙UN ═ICROSYSTEMS' ╙UN╧╙, AND ┬ERKELEY
╒NIX.  ╘HIS OPERATING SYSTEM SUPPORTS SUCH FEATURES AS COMPLETE  FILE  CONTROL,
TEXT EDITING AND PROCESSING, TELECOMMUNICATIONS, PROGRAM DEVELOPMENT AN ON-LINE
HELP.

╒NIX 128 IS NOT A REAL ╒NIX ╧╙.  ┴ "REAL" ╒NIX SYSTEM  IS  MULTIPROCESSING  (IT
CAN  DO  MORE  THAN  ONE  TASK  AT  THE  SAME TIME); HAS TRUE PIPELINING (PIPES
SUPPORTED BY PROCESS FORKS INSTEAD OF DISK FILES); AND IS WRITTEN  IN  ├  (╒NIX
128  WAS  WRITTEN  IN  ├┬═ ┬┴╙╔├ 7.0 AND COMPILED INTO MACHINE CODE WITH ┴BACUS
╙OFTWARE'S ┬ASIC 128 COMPILER).  ╚OWEVER, ╒NIX 128 DOES  RETAIN  THE  LOOK  AND
FEEL  OF  A "REAL" ╒NIX SYSTEM, AS WELL AS SOME UNIX-COMPATIBLE FUNCTIONS (TAR,
TIP, UUENCODE/UUDECODE AND NROFF ARE EXAMPLES).







╒NIX 128 V3.10 ═ANUAL           15 ╩ANUARY 1992                          ╨AGE 2


3.  ╥EVISIONS ╙INCE ╓ERSION 3.00:

═ANY REVISIONS HAVE BEEN MADE  SINCE  THE  LAST  RELEASE  OF  ╒NIX  128.   ═OST
IMPORTANTLY,  THE  OLD SYSTEM OF KEEPING TRACK OF DISK DEVICES (DESIGNATING ONE
DRIVE AS THE 'SYSTEM DRIVE' AND ANOTHER AS THE 'DATA DRIVE') HAS BEEN  FLUSHED.
╘HE  MAIN PROBLEMS WITH THE OLD SYSTEM WERE THAT ONLY TWO DISK DEVICES COULD BE
USED, AND THAT IF YOU HAPPENED TO PUT THE SYSTEM DISKETTE INTO THE  WRONG  DISK
DRIVE  ╒NIX  COULDN'T  FIND  ITS  FILES.   ╘HE  NEW SYSTEM, USING WHAT ╔ CALL A
'PATH', ELIMINATES THESE PROBLEMS BY KEEPING A LIST OF ALL YOUR  DRIVES.   ┼ACH
DRIVE  ON  THE  LIST  IS  SEARCHED  FOR  A  FILE YOU WANT TO READ OR APPEND TO,
ELIMINATING DISK SWAPS.  ╫RITES ARE MADE TO EITHER THE MOST LOGICAL  CHOICE  OR
THE  FIRST DRIVE IN THE PATH, WHICHEVER MAKES MORE SENSE.  ╙EE THE MANUAL ENTRY
ON PATH FOR SPECIFIC COMMAND INFORMATION.

┴ SECOND IMPORTANT REVISION WAS A REVAMPING OF THE WAY PIPES ARE  HANDLED.   ╔N
OLDER  VERSIONS  OF  ╒NIX  128,  PIPES  NEEDED  TO  BE  HANDLED BY EACH COMMAND
SEPARATELY; THIS WENT AGAINST BOTH PRODUCTIVITY AND THE  SPIRIT  OF  ╒NIX.   ╔N
V3.10, THE SHELL HANDLES ALL PIPES.  ╫┴╥╬╔╬╟:  ┘OU SHOULD ONLY ATTEMPT ONE PIPE
PER COMMAND LINE.  ╘HE SHELL TAKES A COMMAND LINE WITH A PIPE, FOR EXAMPLE:
        % A ⌐ B
AND CONVERTS IT TO THE FOLLOWING:
        % A >TMP ; B TMP
(OF COURSE, REAL ╒NIX WOULD SIMPLY FORK TWO CONCURRENT PROCESSES...)
╘HIS IS UNFORTUNATELY A SLOW AND CUMBERSOME METHOD OF IMPLEMENTING PIPES  (REAL
╒NIX  STARTS  TWO  PROCESSES,  AND  REDIRECTS  THE OUTPUT OF THE FIRST INTO THE
SECOND).  ├ONSIDER THE  COMMAND  'MORE  FILENAME  ⌐  LPR';  ╒NIX  128  MAKES  A
DUPLICATE   COPY   OF   THE   FILE   BEFORE  PRINTING  IT,  WHICH  IS  ENTIRELY
COUNTERPRODUCTIVE.  ┴S A SPECIAL CASE, ╔'VE PATCHED AROUND THE  PIPE  MECHANISM
FOR  PIPES  TO  LPR;  ANYTHING  PIPED  TO  LPR  WILL BE PRINTED IMMEDIATELY (NO
TEMPORARY FILES ARE USED).

═ANY BUGS IN VERSION 3.00 WERE REPORTED AND WERE FIXED:
     1.  ╤UOTA USED TO RESET 1571 DRIVES TO 1541 MODE.
     2.  ═AKE AND STARTUP REQUIRED THE USE OF DRIVE 8.
     3.  ╙OME OF THE MENU ITEMS WORKED INCORRECTLY
     4.  ┼MACS WOULD ADD A <├╥> AT THE END OF FILES LOADED IN.
     5.  ALLOC WOULDN'T RETURN THE RIGHT AMOUNT OF ╥┼╒ MEMORY AFTER SWAPS.
     6.  ╘HERE WERE A FEW PROBLEMS WITH THE MANUAL PAGES (TYPOS ETC.)
     7.  TIP:  ╞IXED THE CURSOR ADDRESSING IN BOTH ╓╘52 AND ╓╘100 MODES.
     8.  MAIL, FTP, SPREAD, DC: UPDATED AND ENHANCED.


4.  ┬UILDING THE ╒NIX 128 ╙YSTEM:

╘HE SYSTEM REQUIREMENTS ARE:  A ├OMMODORE 128 COMPUTER, A 1571 DISK DRIVE,  AND
AN  80-COLUMN ╥╟┬ MONITOR.  ┴S MANY DRIVES AS THE BUS CAN TAKE MAY BE SUPPORTED
(NO SPECIAL DRIVE-SPECIFIC CODE WAS USED; JUST ABOUT ANY DISK DEVICE SHOULD  BE
COMPATIBLE).   ┴  PRINTER IS NOT ONLY SUPPORTED BUT RECOMMENDED.  ╥┴═ EXPANDERS
ARE RECOGNIZED (├OMMODORE ╥AM─╧╙ SEEMS TO  BE  TOTALLY  INCOMPATIBLE  WITH  THE
┬ASIC  128  COMPILER;  A ╥┴═ ─ISK SUCH AS THE ├═─ ╥┴═─RIVE SHOULD BE COMPLETELY
COMPATIBLE).  ┴ ├OMMODORE 1670-COMPATIBLE MODEM IS SUPPORTED.

╘HE FIRST STEP IN SETTING UP THE ╒NIX 128 SYSTEM IS UNARCHIVING THE FILES.   ─O
THIS BY RUNNING EACH ARCHIVE PROGRAM IN SEQUENCE.








╒NIX 128 V3.10 ═ANUAL           15 ╩ANUARY 1992                          ╨AGE 3


╬EXT, IT IS NECESSARY TO UNARCHIVE ALL THE  SYSTEM  DATA  FILES.   ─O  THIS  BY
RUNNING THE PROGRAM "═┴╦┼" AND PROVIDING IT WITH THE DEVICE NUMBER OF THE DRIVE
THAT CONTAINS THE SYSTEM DISK.  ╘HIS PROGRAM WILL WRITE A FEW ╙┼╤ FILES (.LOGIN
[SYSTEM INIT FILE],  AUTHOR  [ABOUT  ME],  NROFF.HLP  [THE  NROFF  HELP  FILE],
NROFF.TBL  [THE  PRINTER  TABLE  FOR NROFF], PASSWD [THE SYSTEM PASSWORD FILE],
STDLIB.I [ASSEMBLER MACROS], POLISH.EF  AND  CYRILLIC.EF  [POLISH  AND  RUSSIAN
FONTS  FOR  EMACS],  AMIGA.UF [THE ╒NIX 128 FONT; STOLEN IN PART FROM ─ES╘ERM'S
DES.AMIGASET], AND INVENTIO13 [A MUSIC FILE]) TO THE DISK, THEN CHECK  TO  MAKE
SURE ALL THE REQUIRED FILES ARE PRESENT.


5.  ╠OGGING ╔N ╞OR ╘HE ╞IRST ╘IME:

╘O START THE ╒NIX 128 SYSTEM, TYPE ╥╒╬ "╙╘┴╥╘╒╨".  ╔T WILL LOAD THE SHELL  (THE
COMMAND  INTERPRETER)  AND  ASK YOU FOR YOUR USERNAME AND PASSWORD.  ╒SE 'ROOT'
FOR BOTH.

╘HE LAST SYSTEM FILE THAT NEEDS TO BE WRITTEN IS THE DISK DIRECTORY.  ╘O  WRITE
THIS,  TYPE  %  FSCK  (╔  WILL REFER TO SHELL COMMANDS IN THIS FASHION... THE %
ISN'T ENTERED, BUT REPRESENTS THE SYSTEM PROMPT).  'FSCK'  DOES  A  "FILESYSTEM
CONSISTENCY  CHECK"  WHICH  MAKES  SURE  THE DIRECTORY HEIRARCHY IS CORRECT AND
WRITES THE FILESYSTEM TO THE DISK.  'FSCK' SHOULD BE EXECUTED  ONCE  EVERY  FEW
SESSIONS TO ENSURE THE VALIDITY OF THE FILESYSTEM.


6.  ├USTOMIZATION OF THE ╙HELL:

╘HE SHELL HAS A CONFIGURATION FILE CALLED .LOGIN WHICH MAY CONTAIN A NUMBER  OF
COMMANDS  TO  CUSTOMIZE  YOUR  SYSTEM.   ╘HE  FOLLOWING  IS THE STANDARD .LOGIN
SUPPLIED, WITH COMMENTS ADDED IN THE SECOND COLUMN:

   SET PROMPT=%                   (╙ET THE SYSTEM PROMPT)
   ALIAS F1 ALLOC                 (╟IVE A SHORTENED VERSION OF A COMMAND.
   ALIAS F3 DIR                      ╙EE THE MANUAL ENTRY ON 'ALIAS')
   ALIAS LS LS -╞AS                  (╟IVE COMPLETE DIRECTORIES WITH SIZE...)
   ALIAS HELP MORE HELP.TXT          (HELP --> SHOW THE FILE 'HELP.TXT')
   COLOR 16 1                     (╙ET THE CHARACTER AND BACKGROUND COLORS)
   LOGIN                          (┴SK FOR PASSWORDS [OR 'NOLOGIN'])
   MENU BROWSE\BROWSE             (─EFINE THE MENU THAT POPS UP WHEN ┴╠╘ IS
   MENU EMACS\EMACS                  IS PRESSED.  ╘HE FIRST PARAMETER IS WHAT
   MENU TIP\TIP                      IS SHOWN IN THE MENU; THE SUBSEQUENT
   MENU MAIL\MAIL                    PARAMETERS ARE THE COMMANDS PASSED TO THE
   MENU PUZZLE\PUZZLE                SHELL.  'NOP' DOES NOTHING.
   (...)
   MENU --┼XIT--\NOP

╘HERE IS A SINGLE ACCOUNT SET UP (ROOT); MORE MAY BE  ADDED  WITH  THE  ADDUSER
COMMAND.

╔F YOU HAVE A ╙EIKOSHA ╙╨1000 PRINTER, THE FILE 'NROFF.TBL' IS ALREADY  SET  UP
FOR YOU.  ╔F YOU OWN ANOTHER TYPE OF PRINTER, YOU HAVE TO EDIT '═┴╦┼' TO CHANGE
THE SETTINGS FOR YOUR PRINTER.  ═┴╦┼ IS WELL COMMENTED; JUST FOLLOW THE EXAMPLE
SET BY THE DEFAULT 'NROFF.TBL'.











╒NIX 128 V3.10 ═ANUAL           15 ╩ANUARY 1992                          ╨AGE 4


7.  ╘HE ╙HELL:

╘HE SHELL IS THE COMMAND INTERPRETER FOR  THE  ╒NIX  128  SYSTEM.   ╔T  IS  THE
PROGRAM THAT CONTROLS EVERYTHING THAT YOU DO.  ╔T ALSO KEEPS TRACK OF ALL SORTS
OF DATA FOR YOU.  ╙OME OF THE FEATURES OF THE SHELL INCLUDE (IN  NO  PARTICULAR
ORDER):

(1)  ╞ILE SECURITY:  ╒NIX 128 PROVIDES THE 'CHMOD' COMMAND FOR  SETTING  ACCESS
PERMISSION  FOR INDIVIDUAL FILES.  ┘OU CAN SELECT TO ALLOW OR DISALLOW READ AND
WRITE PERMISSION FOR BOTH THE OWNER OF THE FILE (YOURSELF) AND  EVERYONE  ELSE.
╘HESE  PERMISSIONS ARE SHOWN BY TYPING 'LS -L.'  ╒SERS WITH SUPERUSER PRIVELEGE
(THE PRIVELEGE LEVEL OF A USER IS SET WHEN ADDING NEW ACCOUNTS WITH  'ADDUSER')
CAN READ AND WRITE ANY FILE, REGARDLESS OF THE ACCESS PERMISSIONS.

(2)  ╚ISTORY LIST:  ╘YPE 'HISTORY' TO SEE THE COMMANDS YOU'VE TYPED.  ╘HIS LIST
CAN  BE  USED  IN  CONJUNCTION WITH THE '!' OPERATOR TO RECALL COMMANDS WITHOUT
TYPING THEM AGAIN.  ┴LSO, THE CURSOR  KEYS  (UP/DOWN)  WILL  STEP  THROUGH  THE
PREVIOUS  FIVE  COMMANDS ON THE COMMAND LINE. (SEE THE MAN ENTRIES ON 'HISTORY'
AND '!')

(3)  ┴LIASING:  ╘HE SHELL KEEPS A LIST OF ALTERNATE DEFINITIONS  FOR  COMMANDS.
╘HIS  ALLOWS  YOU  TO  DEFINE  YOUR  OWN SHORT-CUT COMMAND NAMES.  ╞OR EXAMPLE:
SUPPOSE YOU'D RATHER TYPE 'AU' THAN TYPE 'ADDUSER'... YOU CAN SAY  %  ALIAS  AU
ADDUSER.  ╘HEN, WHENEVER YOU TYPE 'AU', 'ADDUSER' WILL BE SUBSTITUTED.  ╙EE THE
MAN ENTRY ON 'ALIAS'.

(4)  ╞ILENAME COMPLETION:  ╔NSTEAD OF TYPING OUT LONG FILENAMES, JUST  TYPE  AN
UNAMBIGUOUS PARTIAL FILENAME AND PRESS THE ┼╙├ KEY.  ╞OR EXAMPLE, TYPING % MORE
.L<┼╙├> WILL FINISH THE LINE TO % MORE .LOGIN, ASSUMING YOU'RE CURRENTLY IN THE
ROOT DIRECTORY ON THE SYSTEM DISK.

(5)  ╧UTPUT REDIRECTION:  ┘OU CAN APPEND A '>' AND A FILENAME TO THE END OF THE
COMMAND LINE; THIS SPECIFIES THAT YOU'D LIKE THE OUTPUT OF A COMMAND TO GO TO A
FILE INSTEAD OF TO THE SCREEN (FOR EXAMPLE: % ALLOC >FILE).

(6)  ╨IPES:  ╨IPES CONNECT TWO PROGRAMS TOGETHER, FUNNELING THE OUTPUT  OF  THE
FIRST  INTO  THE INPUT OF THE SECOND.  ╘HE PIPE SYMBOL IS THE VERTICAL BAR, THE
╙╚╔╞╘-┬RITISH POUND KEY.  ╞OR EXAMPLE, SAY YOU'D LIKE TO SEE ALL THE  LINES  OF
OUTPUT  OF  THE  ALLOC  COMMAND  THAT  CONTAIN  THE PHRASE '═EMORY'.  ┘OU COULD
REDIRECT THE OUTPUT OF ALLOC TO A FILE (ALLOC >FILE) THEN USE GREP  TO  DO  THE
SEARCH,  OR YOU COULD SAY '% ALLOC ⌐ GREP ═EMORY'.  ╘HE SECOND IS A LOT SIMPLER
AND MORE ELEGANT.

(7)  ═ULTIPLE ├OMMANDS:  ┘OU CAN ENTER MULTIPLE COMMANDS ON  A  SINGLE  COMMAND
LINE BY SEPARATING THEM WITH A ';'.  ╞OR EXAMPLE:  % CLEAR;ALLOC WILL CLEAR THE
SCREEN,  THEN  SHOW  MEMORY  ALLOCATION.   ╙PACES  ARE  IRRELEVANT.   ╘HE  ONLY
RESTRICTION IS THAT TOTAL COMMAND LINE LENGTH MUST BE LESS THAN 255 CHARACTERS.

(8)  ╙HELL SCRIPTS:  ┘OU CAN WRITE SMALL SHELL SCRIPTS FOR ╒NIX 128.   ┴  SHELL
SCRIPT  IS  A  FILE  CONTAINING VALID COMMANDS, WHOSE FIRST CHARACTER IS A '!'.
╒NFORTUNATELY, ╒NIX 128 WILL ONLY  ALLOW  A  SCRIPT  OF  TOTAL  LENGTH  OF  255
CHARACTERS.  ┴N EXAMPLE MIGHT BE:
       !CLEAR
       ALLOC
       IOSTAT
╘O EXECUTE A SHELL SCRIPT, SIMPLY TYPE ITS NAME AT THE SHELL PROMPT (%).







╒NIX 128 V3.10 ═ANUAL           15 ╩ANUARY 1992                          ╨AGE 5


8.   ╞ILES AND ─IRECTORIES:

╒NIX 128 USES A DIFFERENT FILE/DIRECTORY STRUCTURE THAN THE ├OMMODORE 128  ─╧╙.
╙PECIFICALLY,  IT  ALLOWS YOU TO CREATE AND REMOVE SUBDIRECTORIES, AND COPY AND
RENAME FILES IN BETWEEN THESE DIRECTORIES.

╘HE DIRECTORY STRUCTURE BEGINS AT THE ROOT DIRECTORY (CALLED 'ROOT' OR '/') AND
BRANCHES  DOWNWARD INTO SUBDIRECTORIES.  ╙UBDIRECTORIES ARE CREATED AND REMOVED
WITH THE 'MKDIR' AND 'RMDIR' COMMANDS RESPECTIVELY.  ╞ILES CAN BE  MOVED  (MV),
COPIED (CP), AND REMOVED (RM).

╒NIX 128 RELIES UPON THE DIRECTORIES  IT  CREATES  ON  THE  DISKETTE  FOR  FILE
INFORMATION-  THE  ├┬═  ─╧╙ DIRECTORY ISN'T USED.  ╙OMETIMES, THESE DIRECTORIES
BECOME CORRUPT, USUALLY THROUGH NON-╒NIX DISK OPERATIONS.  ╔T IS  NECESSARY  TO
ISSUE THE FSCK COMMAND FROM TIME TO TIME TO KEEP THESE DIRECTORIES CURRENT.


9.   ╟ETTING ╚ELP:

╚ELP IS AVAILABLE JUST ABOUT EVERY STEP  OF  THE  WAY.   ╘HERE  IS  AN  ON-LINE
MANUAL,  A  MANUAL  BROWSER FOR EXTENDED MANUAL READING, AND HELP SCREENS BUILT
INTO ALMOST EVERY APPLICATION.  ╚ERE IS A GUIDE ON GETTING HELP:

1.  ╞ROM THE SHELL:  ┘OU CAN TYPE % MAN <COMMAND> TO SEE THE  MANUAL  ENTRY  ON
ANY  VALID  COMMAND  (TYPING  %  COMMANDS  WILL  SHOW THE LIST OF VALID COMMAND
NAMES).  ╔F YOU ARE JUST GETTING STARTED, YOU MIGHT WANT TO TYPE  %  BROWSE  TO
LOOK THROUGH THE MANUAL AT LENGTH.  ┴LSO, TYPING % APROPOS <PHRASE> WILL SEARCH
THE MANUAL FOR A PHRASE AND RETURN THE COMMANDS THAT APPLY.

2.  ╞ROM ╔NDIVIDUAL ┴PPLICATIONS:
    EMACS:  [├╧╬╘╥╧╠]-H  (NORMALLY WRITTEN ├-H) WILL SHOW THE EMACS
            HELP SCREEN, AND '[┼╙├] X NROFF' (NORMALLY WRITTEN ═-X
            NROFF) WILL SHOW THE NROFF HELP SCREEN.
    SPREAD: ├-H WILL SHOW THE HELP SCREENS.
    MAIL:   ╘YPE ? AT THE & PROMPT FOR A LIST OF COMMANDS.
    DC:     ╘YPE ? AT THE DC> PROMPT FOR A LIST OF COMMANDS.
    FTP:    ╘YPE ? AT THE FTP> PROMPT FOR A LIST OF COMMANDS.


10.  ╨RINTING:

╞ILES CAN BE PRINTED IN ONE OF TWO WAYS:

     (1) ─IRECTLY:  ╘O PRINT A  FILE  (OR  LIST  OF  FILES),  YOU  TYPE  %  LPR
FILENAME.  ╔F MORE THAN ONE FILENAME IS GIVEN, THE FIRST IS PRINTED IMMEDIATELY
AND THE SUBSEQUENT FILES ARE QUEUED FOR PRINTING (SWAPPING OUT THE  SHELL  WILL
DESTROY  THE  PRINT  QUEUE.)   ╔F YOU WISH TO DO OTHER THINGS (BESIDES ANYTHING
THAT SWAPS OUT THE SHELL) WHILE PRINTING, PLACE A '&' AT THE END OF THE COMMAND
LINE  (EX:   %  LPR  FOO.TXT&).   ╘HIS  WILL  PRINT  THE FILE IN THE BACKGROUND
(SLOWLY!).  % LPQ WILL SHOW THE PRINTER QUEUE, AND % LPRM WILL REMOVE ALL ITEMS
FROM THE PRINTER QUEUE.

     (2) ├OPYING OUTPUT THROUGH PIPES:  ┴NY TEXT OUTPUT FROM A COMMAND  CAN  BE
RE-DIRECTED  TO  THE  PRINTER BY APPENDING ⌐LPR TO THE END OF THE COMMAND LINE.
╞OR EXAMPLE, % SCREENDUMP ⌐ LPR WILL PRINT THE SCREEN, AND % LPTEST ⌐ LPR  WILL
TEST THE PRINTER.







╒NIX 128 V3.10 ═ANUAL           15 ╩ANUARY 1992                          ╨AGE 6


11.  ╔NTRODUCTION TO FTP

╒NIX 128 V3.10 COMES WITH A  NEW  IMPROVED  VERSION  OF  FTP.   FTP,  THE  FILE
TRANSFER PROGRAM, IS A COMBINATION OF A UNIQUE FILE TRANSFER PROTOCOL AND A SET
OF TERMINAL INSTRUCTIONS DESIGNED TO TRANSMIT AND  RECIEVE  FILES  BETWEEN  TWO
╒NIX  128  SITES.  ╔T IS NOT COMPATIBLE WITH THE ╔NTERNET FTP USED BETWEEN ┬╙─,
─┼├, ╙╒╬ AND OTHER LARGE-SCALE ╒NIX SYSTEMS.

╘HE FTP COMMAND INVOKES ONE OF TWO MODES.   ╘HE  FIRST  MODE  (REMOTE  TERMINAL
MODE)  IS  USED  TO  ORIGINATE  A MODEM COMMUNICATIONS LINK TO ANOTHER ╒NIX 128
SYSTEM.  ╘HE SECOND MODE (SERVER MODE) IS USED TO ANSWER INCOMING CALLS AND ACT
AS A FILESERVER.

╘O INVOKE REMOTE TERMINAL MODE, TYPE % FTP  OR  % FTP PHONE-NUMBER.  ╔F A PHONE
NUMBER IS GIVEN, FTP WILL AUTOMATICALLY DIAL THAT NUMBER AND ATTEMPT TO CONNECT
TO ANOTHER ╒NIX 128 SYSTEM (THE SYSTEM YOU DIAL MUST ALREADY BE RUNNING IN  FTP
SERVER MODE.)

╘O INVOKE SERVER MODE, TYPE % FTP -S.  FTP WILL WAIT FOR  THE  PHONE  TO  RING,
ANSWER IT, AND BEGIN THE SESSION.

11.1  ╥EMOTE ╘ERMINAL ├OMMANDS:
      ╘HE FOLLOWING COMMANDS ARE AVAILABLE AT THE FTP> PROMPT:

?              ╟ET HELP (LIST THE COMMAND SUMMARY)
ASCII          ╙AVE INCOMING FILES AS ╙┼╤, DON'T CONVERT ╨┼╘╙├╔╔<->┴╙├╔╔
BINARY         ╙AVE INCOMING FILES AS ╨╥╟, DON'T CONVERT ╨┼╘╙├╔╔<->┴╙├╔╔
BYE            ╚ANG UP THE PHONE, QUIT FTP AND RETURN TO ╒NIX 128
CD [DIR]       ├HANGE DIRECTORY TO [DIR]
CLOSE          ╚ANG UP THE PHONE BUT DO NOT EXIT FTP.
CONVERT        ┬INARY CONVERSION OF ╨╥╟ FILES TO ╙┼╤ FILES.
DIR            ╥EAD CURRENT REMOTE DIRECTORY
GET [FILE]     ╟ET A FILE FROM THE REMOTE SYSTEM.  ╙ELECT ASCII, TEXT, OR
               BINARY FIRST TO ASSURE THE PROPER FILE TYPE AND CONVERSION.
HASH           ╙HOW A HASH MARK (#) FOR EVERY 512 BYTES TRANSFERRED.  ╘HIS
               COMMAND TOGGLES HASH MARK PRINTING ON AND OFF.
OPEN [NUMBER]  ─IAL A PHONE NUMBER AND ATTEMPT TO CONNECT TO A REMOTE SYSTEM.
SEND [FILE]    ╙END A FILE TO THE REMOTE SYSTEM.
SERVER         ╔NVOKE SERVER MODE FROM REMOTE TERMINAL MODE.
TEXT           ╙AVE INCOMING FILES AS ╙┼╤ FILES, CONVERT ╨┼╘╙├╔╔<->┴╙├╔╔
               (╘HERE IS ALMOST NO NEED FOR THIS COMMAND.  ╫HEN IN DOUBT,
               USE ASCII AND CONVERT LATER WITH 'DD -S')

11.2  ╙ERVER ├OMMANDS:

      ╘HE ONLY INPUT THE SERVER ALLOWS IS ├╘╥╠-C OR ├╘╥╠-Z, AND IT ALLOWS THESE
ONLY  IF  SOMEONE  IS NOT CONNECTED TO YOUR MACHINE AT THE TIME.  ├╘╥╠-C BREAKS
BACK TO ╒NIX 128, AND ├╘╥╠-Z BREAKS BACK TO TERMINAL MODE.  ┴LL FILE  TRANSFERS
AND DIRECTORY REQUESTS ARE AUTOMATIC.  ╘HE NEW VERSION OF FTP (V2.00) NOW SENDS
FILETYPE INFORMATION WITH GET AND SEND REQUESTS (THE OLDER VERSION OF FTP SAVED
EVERYTHING AS UN-TRANSLATED PROGRAM FILES).












╒NIX 128 V3.10 ═ANUAL           15 ╩ANUARY 1992                          ╨AGE 7


11.3  ╘HE FTP ╨ROTOCOL:

FTP USES A SPECIAL MESSAGE-PASSING ╪-═ODEM DERIVED PROTOCOL FOR FILE TRANSFERS.
╞IRST,  A  REQUEST  GOES  FROM  THE REMOTE TERMINAL TO THE SERVER TELLING IT TO
EITHER SEND OR RECEIVE A FILE.  ╘HE FILE IS SENT IN  128  BYTE  BLOCKS  IN  THE
FOLLOWING FORMAT:
                    [ 127 BYTES OF DATA ] [ CONTROL BYTE ]
╘HE CONTROL BYTE IS ONE OF THREE VALUES.  ╔F IT IS 0, ANOTHER BLOCK IS  COMING.
╔F  IT IS ├ONTROL-┘ OR ├ONTROL-┌, THEN THIS IS THE LAST BLOCK AND THE LAST BYTE
OF VALID DATA IS THE ONE THAT IS NOT EQUAL TO THE CONTROL  BYTE  (╔F  THE  LAST
VALID  BYTE  IS  NOT ├ONTROL-┌ THEN THE CONTROL BYTE WILL BE ├ONTROL-┌.  ╔F THE
LAST VALID BYTE IS ├ONTROL-┌, ├ONTROL-┘ WILL BE THE CONTROL BYTE.)

┴LL DATA CONNECTIONS ARE MADE WITH 8 DATA BITS, NO PARITY, 1 STOP BIT, AT  1200
BAUD.